::std::equal(m.begin(), m.end(), p)

raises the following warning:

C:\Program Files\Microsoft Visual Studio 8\VC\include\xutility(2674) :
warning C4996: 'std::_Equal' was declared deprecated
        C:\Program Files\Microsoft Visual Studio
8\VC\include\xutility(2661) : see declaration of 'std::_Equal'
        Message: 'You have used a std:: construct that is not safe. See
documentation on how to use the Safe Standard C++ Library'

Wow. Thanks a lot. The same thing happens for a whole raft of other
standard functions, such as copy, set_difference, replace, remove,
merge, etc.

Note the interesting wording: 'std::_equal' was declared deprecated. I
was under the distinct impression that only the C++ standards committee
could deprecate anything in the std namespace...

The work-around is not pretty either. You have to basically redefine
all the affected templates:

namespace PortabilityHacks
{
    template<class InputIterator1, class InputIterator2>
    bool
    equal(InputIterator1 first1, InputIterator1 last1, InputIterator2
first2)
    {
#if _WIN32 && _MSC_VER == 1400
        return ::stdext::unchecked_equal(first1, last1, first2);
#else
        return ::std::copy(first1, last1, first2);
#endif
    }

Having written the workaround, I can go and add the PortabilityHacks
namespace to all points where I call one of the standard template
functions that MS have decided to deprecate. My big thanks for this
change go to the MS C++ team: you have just broken my code in many
hundreds of places :-(

I can disable the warning by setting the warning level to 4, but that
doesn't really help me. For one, I don't like to disable warnings;
certainly not with a pragma in a header file because that affects all
the customer code that includes my header file, and also not with a
compiler option. I like my code to compile clean, without warnings.

If this misfeature is the Visual C++ team's idea of standard
compliance, I'm not impressed :-(

Michi.