Slight inline documentation updates.

- Fix #314: documentation for `finally` should use the word "settling" instead of "rejection."
- Use "thenable" more often, to reflect real behavior.
- Use "settled" in place of "resolved" where appropriate.
- Rewrite `defer` inline documentation to match reality.
Infinite long stack traces!! Closes #144.
Switch to `longStackSupport` (default `false`).

This replaces `longStackJumpLimit`, as that concept was not well-conceived. It also changes the default from turning on long stack traces to turning them off.

Fixes #264.
Version 0.9.5 release notes
Correction to change log

Generators for ES6 were introduced in previous release.
0.9.5

(Minified)
Bandaid for recognizing inspectable promises

This helps but does not fix the problem of recognizing our own brand of
promises, as distinct from promises from earlier versions of Q or other
libraries (promise-alikes).
Reimplement nextTick

- max priority for process.nextTick
- support for node domains
Make all promises inspectable by default

Custom promises have a state of "unknown" by default.  All custom
promises have an "inspect" method, regardless of whether one is
specified.
Move implementation from when to then

This eliminiates a problem with infinite coercion.  The job of "when"
becomes simply to coerce and call "then".  "then" may assume that "this"
is a promiseDispatch branded promise.
Rename makePromise to Promise internally, for the debuggers
Merge pull request #316 reimplementing nextTick
0.9.6

-   Minified
-   Changelog update
Fix lint errors.
Update README - Adapting node
Merge pull request #321 from CGamesPlay/master

Add clarification regarding Node.js CPS to README.md
Rename delay to throttle, add delay

throttle() delays promises at most until the given time has passed since creating the promise. This is what delay() used to do.

delay() inserts a delay anywhere between resolutions (succeeded or rejected) in the promise chain. This is what jQuery users are used to.
Grunted
Make delay work only on success, remove throttle
Beginnings of a performance testing suite.

Use `npm run benchmark`.