scan call should emit _either_ a scanError or scanFinished.

In case of an error, such as 'Operation already in progress', the scan for
the particular call to scan was never started (it ended with an
error) so it can never be finished.

The documentation for callWithCallback states it will call the
error method _instead_ of the return method in the case of an error.

I can see the need for a scanInProgress property or somesuch.
Merge pull request #53 from lpotter/master

scan call should emit _either_ a scanError or scanFinished.