No disagreement on any of that. I was mostly wondering who uses VS2010 anymore, and curious to know if the bug still exists in newer versions of Visual Studio (but not curious enough to bother testing it).
Yea at my work we have some legacy solutions that depend on libraries that were built with the 2010 compiler but the source is not available and the library shares stl containers on the boundaries. Therefore we're forced to create wrapper libraries that encapsulate the 2010lib and use things like char* ptrs instead of strings on the library API. Those wrapper libraries need to use the 2010 compiler and then we can add those libraries to our modern solutions without having mismatched definitions of stl containers.
