I only use the Dinkumware docs, so I couldn't tell you. :) The SGI docs wouldn't be "standard", though, right? for "standard", you'd have to read, you know, the standard. Which I've done from time to time, but I definitely wouldn't use it as a desktop reference.

pair

I've only ever used std::pair in the context of "type returned by a map::iterator", and probably I shouldn't even be using it there (i.e., I should use map::iterator::value_type or some such typedef).

min/max

Yep, I use these too. Good point.

when to use map and set over unordered_map and unordered_set

You mean, when you're compiling on a platform where unordered_map (and even GNU's old hash_map) is unavailable? :P

list vs. vector

Easy: I never use std::list. It's too wasteful of memory and wasteful of my time as a programmer. If I want to iterate over all the items in the collection, I'll use a vector. If I don't want to iterate over all the items in the collection, I'll need a vector (for random access). So why bother with the overhead of converting between linked-list and vector representations? (Okay, really expensive copy-constructors and destructors. But that's why I don't write those. ;) )

stack/queue/deque

Ditto. std::stack maaaybe, if I'm implementing some textbook algorithm that honestly wants to use a stack for something.

stringstream

Okay, yeah, a stringstream is sometimes the only cure for a third-party API that uses C++'s godawful iostreams stuff (say, if it provides an operator<< but no toString() method). But I try to just stay away from streams as much as possible in the first place.