http://akkartik.name/codelog.html (from 2005; now I use git instead of darcs)
No one has time to commit EVERYTHING they may want to undo. Also, browsing through history in a version control system takes much longer than dragging a slider.
Another useful case for it is when you're just putting in a bunch of debugging statements that you don't want to be committed later. I find myself doing undo/redo all the time for doing stuff like this. I think a more advanced undo/redo would definitely help out.
That's why you squash the commits when you are done with the profiling. Squashing the commits makes it seem like just one commit (and one commit message) in the log.
This way your log is clean, but you get the advantage of frequent saves.
If you dont want to do this, you could probably hook up something with FUSE