title: Clarification on the "object pool" pattern?
body: <p>I was under the impression that an <code>object pool</code> is a design pattern used for managing a group of pre-allocated objects to which a client can request and be returned one of these objects.  However, it seems that <code>boost.pool</code>'s <code>object_pool</code> class has more to do with lower-level memory management than object management.  Why did they go with this name, as opposed to something like <code>memory_pool</code>?  Am I under the wrong impression that boost's object pool is really a memory pooling scheme?  Or are they essentially the same thing?  Also, why hasn't there been a standard implementation of a more high-level object pool pattern?</p>