As for offering to let someone inspect your code... What coding standards are there, how long do they have to inspect it. Are they going to inspect each sub release, and as we all know, just because we can't find the hole doesn't mean it's not there.
This. Let's assume it's acceptable at on the onset; what if something changes five years down the road. If you're seriously going to use this as an attack platform, you'd be willing to commit to the long-con.
Regarding third party vendors, Dell, HP, etc., the way I've always handled it in the past was to leave any sort of remote access disconnected/disabled until it was needed, and then have someone monitor/oversee everything the technician does. Giving a vendor free-reign 24/7 certainly seems to create an unnecessary exposure.