Re: not a warning?

Inclusion
of a header should not have side effects on compiler settings unless it is
clearly documented as the header's purpose.

No argument from me on that - I agree.

If it is not for a macro why cannot they use #pragma warning(push)/#pragma
warning(pop)?

I haven't checked, but I wondered if the template implementation may
require those warnings remaining suppressed throughout any possible
use of the templates?

Dave
.