Add hash map implementation with less allocation overhead.
Use alternative hash map to safe allocations in Win32Timer.rearm().
Add a "quit" link to the benchmark application.
Move the benchmark application to the example folder and add a HTTP request benchmark.
The HTTP request benchmark now disables request compression.

The gzip compression was taking up a considerable amount of time during the server benchmark.
Further allocation reductions.
Revert the path optimization.

Was corrupting results as soon as a Path object was moved. Unfortunately, because of the support for sub paths and some other features, this kind of optimization is theoretically not possible. An alternative should be to either avoid use of Url/Path in the HTTP server/client or to extend them to use a custom allocator.
The benchmark examples now use VibeManualMemoryManagement to get more meaningful results.
Disable VibeManualMemoryManagement again as it causes a memory leak and doesn't help much with performance.
Content-Type should specify charset for JSON responses

UTF-8 is indeed the default, but this prevents encoding issues in Webkit browsers. 

"JSON text SHALL be encoded in Unicode. The default encoding is UTF-8."
http://www.ietf.org/rfc/rfc4627.txt
Merge pull request #197 from HowToMeetLadies/patch-1

Content-Type should specify charset for JSON responses
Updated change log.
Correct incomplete sentence.
Fix compilation of the REST interface generator by using the new requestHttp variant with scoped callbacks.
Updated VisualD project file.
Merge branch 'master' of github.com:rejectedsoftware/vibe.d
Extended the HTTP request benchmark example to be configurable in the number of concurrent requests and minimum request time.
Add HttpServerSettings.sslContext in favor of the sslKeyFile/sslCertFile fields.

The SSL context is now only created once during initialization instead of for every new connection. Note that still an SSL state is created for every connection.

The old way to specify the SSL credentials still exists but will be deprecated at some point.
Small refactoring (rename the HTTP stream parameters/variables for more clarity).
HttpServerResponse.writeBody(string) now specifies UTF-8 charset by default + default error page is written using writeBody now.