It seems FlushFileBuffers() doesn't set end-of-file (and therefore can lead to corrupted files)

Question

Consider following sequence of calls captured with process monitor:

Here is what happens here:

1. file is opened
2. 15-bytes file write
<