.gitignore: ignore Doxygen database
drop unneeded doc/diagram/.gitignore
Drop thirdparty JSON implementations/performance tests

With the implementation of the more elaborate benchmarking
suite at https://github.com/miloyip/nativejson-benchmark,
the thirdparty performance tests are superseded.
performance.md: reference new benchmark suite
Merge pull request #180 from pah/cleanup/doxygen-thirdparty

Drop thirdparty libraries and minor cleanups
Add customization macros for global new/delete

As mentioned in #181, some environments may require adaptations to
the internal calls to the global `new`/`delete` operators, like
adding explicit `NULL` checks to `delete.

This patch adds two new macros
 * RAPIDJSON_NEW(x)
 * RAPIDJSON_DELETE(x)
to allow user-defined expressions in these cases.

This fixes #181 in an alternative manner.
Merge pull request #183 from pah/feature/wrapped-new-delete

Add customization macros for global new/delete
Add unit tests for StringBuffer.
Stack<>: add _ suffix to member ownAllocator_

For consistency, all member variables should follow the same pattern.
MemoryPoolAllocator, Stack: lazily allocate Allocators

In order to make the constructors more efficient, especially
in the context of C++11 move semantics, the (dynamic) allocations
in MemoryPoolAllocator and Stack should be performed lazily.

Move the allocations to the first use of the allocator in both
classes.
DocumentMove tests: compiler error due to -Wsign-compare

On GCC 4.9, the documenttest.cpp fails to compile in C++11 mode,
as the MoveConstructor/Assignment tests contain left-over
comparisons between signed and unsigned expressions.
Merge pull request #184 from drewnoakes/master

Add unit tests for StringBuffer
Merge pull request #187 from pah/fixes/sign-compare

DocumentMove tests: compiler error due to -Wsign-compare
Merge pull request #188 from pah/feature/lazy-alloc-allocators

MemoryPoolAllocator, Stack: lazily allocate Allocators
Document traits of types using <type_traits> and static_assert in tests.

The tests state the current traits of types Document, Value and
StringBuffer. There are slight differences between them. It seems like a
good idea to extend this approach across more types, and to review the
expected traits across the board.
Merge pull request #189 from drewnoakes/feature/static_assert

Document traits of types using <type_traits> and static_assert in tests