Another one of the new features of VS2005 is a checked STL implementation. Iterators and containers now perform bounds and sanity checking before and after use to determine improper usage. Despite using the STL regularly for three years, it highlighted two very silly mistakes that I would have otherwise missed on VS2003. Do yourself a favor and get decent code coverage under a checked STL implementation. The results may surprise you - and prevent a mysterious crash further down the road.

So it does, awesome. From my simple test, the diagnostics are fairly useful as well.

Of course, that means that debug builds will be even more slow than they were before, which means people will be even more likely to naively discard the standard library as too slow without proper testing.

CM

Of course, STLPort has had a checked STL implementation for quite some time now.