Unhandled EPERM error on Windows when dir deleted

[jgoz]

On Windows, when a watched directory is deleted, an EPERM error is thrown when attempting to stat the change. This can be observed by running the test suite on Windows:

> sane@0.8.0 test 'C:\path\to\sane'
> mocha --bail


  ....................

  19 passing (26s)
  1 failing

  1) sane in normal mode sane(file) removing a dir will emit delete event:
     Uncaught Error: EPERM, stat 'C:\temp\path\to\sane_test\sub_9\file_0'

This happens because fs.stat on win32 will receive an EPERM error instead of ENOENT when attempting to stat a non-existent directory. As far as I can tell, this is similar but not related to nodejs/node-v0.x-archive#4337.

A pull request fixing the issue will be forthcoming.