TPIE 1.1 release

New features in TPIE 1.1:

The pipelining framework makes it easier to implement efficient
streaming algorithms. For more information about the pipelining
framework, see doc/pipelining.dox, or read the documentation on the TPIE
homepage.

The serialization framework provides streaming primitives for working
with item streams where items vary in size. A particular practical use
is for streams of polygons or polygonal line segments. We use the term
`serialization stream', because it requires that items are
(un)serializable (rather than trivially copyable, which is the
requirement in file_stream).

If you have previously run off the TPIE master branch, notice that we
have changed the pipelining API recently to be more internally
consistent.

Other changes since TPIE 1.0:

To get the number of workers used by the TPIE job framework, use
tpie::default_worker_count(). (65c1de4)

We now support Boost filesystem version 3 (34ac4be).

The array implementation has changed, removing segmented_array which
nobody used anyway. This makes the array implementation much simpler and
less error-prone. The TPIE array now supports custom allocators, and it
has specialized std::copy so that an efficient memcpy implementation (or
similar) may be used automatically. (fad27fe and 2f79196)

The memory manager now has switched from a protected integer to an
atomic primitive to keep track of used memory, speeding up non-debug
builds. (7a4189a)

The progress_indicator_arrow class no longer sends unnecessary updates
to the standard output stream. (cc15583)

The new memory manager enforcement level ENFORCE_DEBUG functions like
ENFORCE_WARN, except that memory overusage warnings are sent to
log_warning() rather than log_debug(). (8394479)