I agree with what has been said. Disk space is a big issue. Also if your restore fails part way through will SQL server have enough resources to "roll back"?

I dislike the way restore operates from the GUI anyway. If my restore is not an exact overwrite of the backup then things get tricky. Unlike many of the Microsoft dialogs it does not warn you that you are about to overwrite existing files. I think that is should. It also does not warn you that referenced directory paths don't exist. For example some of my customers have databases on D: and for me D: is the DVD drive. Even if I use the "force restore over existing database" it does not always put the files in the right place.

Would many of your concerns be addressed if the GUI restore tools were improved?