After consideration of issue 4120 and issue 4566, it seems to me that
executables created by bdist_wininst will have a manifest referencing
the MSVC9 assembly, and thus will be in a similar position to the .pyd
files in issue 4120 - that unless the assembly is installed globally or
next to the executable itself, the executable will not start.  Note that
I have not verified this, but have verified the final installer
executable references the CRT assembly, and given those other bugs,
expect it to be true.

It seems to me a reasonable solution would be to have the bdist_wininst
stub use a static copy of the C runtime library.  While this means 2
copies of the CRT will eventually be loaded and would otherwise be
considered evil, the way the stub dynamically loads Python and the few
API functions it uses means it might be reasonable in this case.  Would
the trivial patch which achieves this be desired?