200 instead of 416 with inverted byte range requests

We are using IIS7 and have come accross this issue:

In case where a request contains a range header with an inverted range, e.g. "Range: bytes=101-100" IIS gives a 200 OK response and serves the entire file. The expected behavior would be a 416 Requested Range Not Satisfiable response and no data.

Is this a known bug of IIS and do you know of any workaround?