I came across something weird. I think I have further proof that the option(s) "Defrag freespace" must be recoded/re-programed.
The following happened:
1. Before I used the option "Defrag freespace" I had no fragmented files on my drive. but after I used this option I had three (!!) defragmented files.
2. I then manually defragmented these three files. Two files were defragmented without any strange behaviour. But the third file showed some weird behaviour. It was moved from spot X to a place with plenty free space and was defragmented. But apparently the program was satisfied and - according to the drivemap - moved the file back to that very same spot X, this time the filelist said that it was defragmented. It probably wasn't the very same spot were it was "pulled" from but it certainly looked like it.