NTFS: Bug in sparse file handling

I found a bug in my sparse file handling code. It's a pretty obvious bug but the impact is nonexistent if you always pass uninitialised byte arrays into the read method (hence why I didn't notice it earlier.)

However if you happen to reuse a byte array for a buffer, this can result in some previous data being left the buffer where it should have been zeroed out.