Fix the issue when the loc/range would sometimes include a leading whitespace.

Summary:https://code.google.com/p/esprima/issues/detail?id=501
markStart() was not always preceded by skipComment(). Moving the
skipComment() inside instead.

Test Plan: npm test
Update jQuery Mobile in the benchmark corpus to version 1.4.2.

https://code.google.com/p/esprima/issues/detail?id=354
Forgot to recount line start at string literals with escaped new line

https://code.google.com/p/esprima/issues/detail?id=504
Fixes range of line comment

https://code.google.com/p/esprima/issues/detail?id=506
Update ESLint to 0.4.3.

https://code.google.com/p/esprima/issues/detail?id=473
Show RME for total time in the benchmark script.

https://code.google.com/p/esprima/issues/detail?id=115
Use field instead of an array in LocationMarker

https://code.google.com/p/esprima/issues/detail?id=424
Syntax tree regression check.

Parse every library found in the corpus and produce its syntax tree.
This will be compared against the baseline to ensure that there is
no parsing regression.

https://code.google.com/p/esprima/issues/detail?id=509
Add the baseline syntax tree for all the libraries.

https://code.google.com/p/esprima/issues/detail?id=509
Parser demo should use comment attachment.

Since attaching comments to the syntax node is implemented, this is what
should be instead and not just comments collection.

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

http://code.google.com/p/esprima/issues/detail?id=388
Minimize the payload for npm.

Selectively choose which files to include in the module (for npm).
Currently, this is known to break npat=true when doing npm install.

https://code.google.com/p/esprima/issues/detail?id=493
https://code.google.com/p/esprima/issues/detail?id=510
Master branch for future 2.x releases.

https://code.google.com/p/esprima/issues/detail?id=513
Automatically rewritten for npm.