Mention build tools like r.js, prune.js in readme
Improve throwError coverage

http://code.google.com/p/esprima/issues/detail?id=388
Improve parseParams coverage

http://code.google.com/p/esprima/issues/detail?id=388
Improve parseObjectInitialiser coverage

http://code.google.com/p/esprima/issues/detail?id=388
Update code coverage report.

http://code.google.com/p/esprima/issues/detail?id=388
Bump our coverage threshold.

http://code.google.com/p/esprima/issues/detail?id=388
Update esmorph.

This fixes the unescaped double quotes issue in the function tracing
demo.

http://code.google.com/p/esprima/issues/detail?id=394
Automate the tracking of code complexity.

Use complexity-report (https://github.com/philbooth/complexityReport.js)
as part of the testing. For now, check agains the threshold of
cyclomatic complexity only.

http://code.google.com/p/esprima/issues/detail?id=395
Update to the right version of esmorph.

http://code.google.com/p/esprima/issues/detail?id=394
Track code coverage based on absolute thresholds.

Taking advantage of new Istanbul feature, we can guard against coverage
regression by specifying maximum uncovered entities, instead of
percentage-based thresholds.

See https://github.com/gotwarlost/istanbul/issues/25 for details.

http://code.google.com/p/esprima/issues/detail?id=388
Run a simple script which shows the most cyclomatic-complex functions.

http://code.google.com/p/esprima/issues/detail?id=395
Reduce the cyclomatic complexity of numeric literal scanning.

Spin off the hex and octal handling to two separate functions. This
decrease the cyclomatic complexity of scanNumericLiteral from 28 to 19.

http://code.google.com/p/esprima/issues/detail?id=396
Merge branch 'master' into harmony

Conflicts:
	esprima.js
Adjust code coverage thresholds from this harmony branch.

http://code.google.com/p/esprima/issues/detail?id=388
Adjust the complexity threshold for this harmony branch.

http://code.google.com/p/esprima/issues/detail?id=395