Wow, another amazing catch, great work!

Turns out, this is another side-effect of changes in the new runtime libraries in VS2012.

I've just debugged this and have added a fix for it in 4.64.

Thanks for the report!

Ruud