trying to fix issue reported by Jesse Perla when using some combination of VS2008 and Intel C++ 10.1.020 as build environment.
(I couldn't reproduce the issue with Intel C++ 10.1.011 used via bjam --toolset=intel-win, so I'm unable to say whether this patch fixes the issue.)