Remove feature that [[Call]] can return Reference

http://code.google.com/p/esprima/issues/detail?id=81
Fix invalid start location for CallStatement

CallStatement was returning a position of '(' as a start location. It should return the position of the actual beginning of the statement instead. Example

  parse("universe(42)")

was returning
  {
    type: 'CallExpression',
    ...
    range: [0, 12]
  }

while it should
  {
    type: 'CallExpression',
    ...
    range: [8, 12]
  }

Update the wrapper function and fix tests.

http://code.google.com/p/esprima/issues/detail?id=278
Update ZeParser to revision 0072a617 (May 29 2012).

http://code.google.com/p/esprima/issues/detail?id=292
Mention documentation tool: JFDoc and JSDuck.
Speed comparison test: update parse-js to UglifyJS 1.3.2.

http://code.google.com/p/esprima/issues/detail?id=293
Chrome 20 makes it 3x faster.
Relational operators incorrectly associate to the right

http://code.google.com/p/esprima/issues/detail?id=299
Mention Harmonizr.
Include line and column location for all comments.

http://code.google.com/p/esprima/issues/detail?id=233
Ensure that empy line comment is properly collected.

http://code.google.com/p/esprima/issues/detail?id=276
Minor code shuffling in comment handling to minimize the operations.

http://code.google.com/p/esprima/issues/detail?id=233
Exclude any line terminators in a line comment.

http://code.google.com/p/esprima/issues/detail?id=276
Update CodeMirror to version 2.31.

http://code.google.com/p/esprima/issues/detail?id=300
Location for each comment should honor the options.

'range' and 'loc' in the parsing options will define whether the
index-based and line/column-based location info for each comment will be
available or not. This is done for consistency.

http://code.google.com/p/esprima/issues/detail?id=233
An example to find out token distribution.

http://code.google.com/p/esprima/issues/detail?id=301
Update CodeMirror to version 2.32.

According to CodeMirror web site:

23-07-2012: Version 2.32:
Emergency fix for a bug where an editor with line wrapping on IE will
break when there is no scrollbar.

http://code.google.com/p/esprima/issues/detail?id=300
Supports AMD.

As recommended by James Burke, using UMD pattern
(https://github.com/umdjs/umd) permits using Esprima also with an AMD
loader such as RequireJS.

A new manual test has been added to verify that this AMD loading works.

http://code.google.com/p/esprima/issues/detail?id=291
Include line and column location for all tokens.

http://code.google.com/p/esprima/issues/detail?id=232
Location for each token should honor the options.

'range' and 'loc' in the parsing options will define whether the
index-based and line/column-based location info for each token
will be available or not. This is done for consistency.

http://code.google.com/p/esprima/issues/detail?id=232
In the parser demo, the tokens now follow the location settings.

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