I think we are all coming at this from different perspectives so I will try to be generic in my answers as well as clarify my own preference.
1. For me some of the concerns are raised are not as important to me because my concern is time savings and if some of the underlying data was changed due to a defrag or the startup on the prime drive then so be it. I would have lost this anyway and the product does a good job today at reporting a recovery failure.
2. The text list is basically useless for me for it does not do anything nor does it save me any time .. just fun for searching with wild cards which is usefull - but I would certainly not take the feature out for I like the record aspect of it.
3. Thanks for the note on the filtering / this was my own mistake / very nice - thank you.
4. I would assume that the data structure currently used would have to be stored on a disk that was not in use or at ones discretion for it would write over some areas. - In my past we used to record the free space in order to write protected blocks without damaging data but that was a long time ago and I do not know if the current disk architecture makes these techniques obsolete.
5. I would not expire the list simply report the date / drive for the header. The reason I say this is I personally would like to compare more than one list at a time but with a lot more detail only found in the online version.
6. As to the size of the list - this is not an issue for me based on the the fact that the current list is only in RAM. As to the much larger systems I am not sure if this program would be used for they are probably RAID and if we all start to get to this size then all other factors will change too.
To emphasize the point I just had to scan again - 20hrs and the drive went wonky(technical term ) again so I had to wait another 20hrs. .....