Would anyone care to explain why Recuva won't delete files in the MFT zone?
If anything, why won't it remove the "directory entry" of the file that's been securely deleted through Recuva?
After all, there is a setting that lets you hide securely-deleted files, but these files are still present especially after a rescan.
I would hazard a guess that it is one or more of:
1) The O/S has control of the MFT and Recuva can't access it at all
2) Recuva can access the MFT but can't lock it to do changes
3) It manage the MFT effectively means managing the entire pc whilst doing changes
4) To mess up a file is unfortunate, to mess up the MFT is a pc rebuild
5) Piriform wouldn't touch the MFT with a barge-pole