Prototype fix for TLS issues on windows

gh-106 raises some issues with fibers in Windows. The root cause is that
fibers is not finding the v8 TLS origin correctly. This is a new
approach that should be more dependable.
Find thread local slots using v8 isolate pointer

Add __stdcall to correct declaration of find_thread_id().
Then search back in the latest 20 slots for the v8 isolate pointer.
Don't short circuit failed tests

A couple of these tests are less than dependable, so be sure to run all
of them instead of just some of them.
Support for node v0.11.x

Simple wrappers that prefer the new v8 API but support the legacy API as
well. Also improves the build process by adding support for Debug builds
and detects binaries that are broken somehow.
Remove line continuations in Unwrap()

These are leftover from the converted macro. Doesn't affect compilation
at all but is poor style.
Fix for when TLS is 0

The technique in 21213cdf fails when v8 is the first caller of
pthread_key_create. This modifies the function to search all the way
down to 0 instead of just 1.
Bump npm version -> 1.0.1
Support for node v0.11.3

The v8 API is a moving target, isn't it? Closes gh-123.
Update README

Windows 8 is supported.
Detect failure to create coro stacks

If you are creating a lot of fibers (2000~) on a 32-bit system it's very
possible you will run out of addressable memory. This detects a failed
fiber creation and will throw a JS exception. However, if you are that
close to the memory ceiling it's likely that v8 is about to crash as
well.
Support for node v0.11.4

Closes gh-130

More work will likely need to be done before node 1.0 to remove the
deprecation warnings.
Creating full documentation for the Future library
Documentation errors

Just noticed I pulled in the wrong PR for the Future documentation and
there are some errors. As discussed in:
https://github.com/fresheneesz/node-fibers/commit/28b1a4ab3b29a21a48ec7c109b47a7b88a0cf930
Merge remote-tracking branch 'laverdet/master'