title: Practical summary/reference of C++11 containers/adapters properties?
body: <p>I'm looking for a comprehensive summary/reference of important properties of the various C++11 standard containers and container adapters (optionally also including boost/Qt), but <strong>indexed by those properties</strong> rather than the usual per container documentation (more on that below).</p>
  
  <p>The properties I have in mind include, from the top of my head:</p>
  
  <ul>
  <li>Insertion capabilities (front / back / arbitrary).</li>
  <li>Removal capabilities (front / back / arbitrary).</li>
  <li>Access capabilities (front / back / uni/bi-directional traversal / random access).</li>
  <li>Complexity of the aforementioned operations, and iterator invalidation rules.</li>
  <li>Uniqueness? Ordered? Associative? Contiguous storage? Reservation ahead of time?</li>
  </ul>
  
  <p><sup>I may have forgotten some in which case don't hesitate to comment/edit.</sup></p>
  
  <p>The goal is to use that document as an aid to choose the right container/adapter for the right job, without having to wade through the various individual documentations over and over every time (I have a terrible memory).</p>
  
  <p>Ideally it should be indexed both by property and by container type (eg. table-like) to allow for decision-making as well as for quick reference of the basic constraints. But really the per property indexes are the most important for me since this is the most painful to search in the documentation.</p>
  
  <p>I'd be very surprised if nobody had already produced such a document, but my Search-fu is failing me on this one.</p>
  
  <p><strong>NOTE:</strong> I'm not asking for you to summarize all these informations (I'll do that myself if I really have to, in which case I'll post the result here) but only if you happen to know an <strong>existing</strong> document that fits those requirements. Something <a href="http://en.cppreference.com/w/cpp/container#Member_function_table" rel="nofollow">like this</a> is a good start but as you can see it still lacks many of the information I'd like to have since it's restricted to member functions.</p>
  
  <p>Thanks for your attention.</p>