   A good reason against STL ?
  Hi!I'm new to STL and I've discovered something I ws not aware of. I'm using a std::deque<Test> where Test is a simple struct made of two integers.When I add a number of these structs, everything works fine, but the very bad thing is when I hit a breakpoint, I'm unable to browse my deque content as I could have done with a home made implementation. I noticed I could perfectly see the deque content when using a simple type like a std::deque<int>Of course I guess that drawback is nothing compared to everything positive that the STL brings me. What do you think ?(or an I not using my debugger correctly ? It is Visual C++ express's)   
  Looks to me like a problem with the debugger, not with the deque. In my case, it complains of a division by zero and thinks the deque contains over 10k elements...   ;  Yeah, it can sometimes be difficult to debug with stl structures. However, the values are usually locatable through the debugger, you may just have to poke through the element list to find it...   ;a picture of my symptoms#define T_MTMessageQueue(_fnRetType) template <class MSG_T> _fnRetType MTMessageQueue<MSG_T>// Sourcetemplate <class MSG_T> class MTMessageQueue{public:void PushMessage(const MSG_T& _msg);bool PopMessage(MSG_T& _msg);private:// behavior:std::deque<MSG_T> m_queue;MTCriticalSection m_criticalSection;};/////////////////////////////////////////////////////T_MTMessageQueue(void)::PushMessage(const MSG_T& _msg){PROTECT_SECTION(&m_criticalSection);m_queue.push_back(_msg);}/////////////////////////////////////////////////////T_MTMessageQueue(bool)::PopMessage(MSG_T& _msg){PROTECT_SECTION(&m_criticalSection);if( m_queue.size() != 0){_msg = m_queue.front();m_queue.pop_front();return true;}return false;};  This might help a bit: VSEDebug VS.NET Debugging Enhancement