Hi Tom! That's right – there’s currently no way to load previous project versions directly within CaseComplete. Requirements.cc comes the closest - it keeps track of what changes with every upload. If you fail to upload each time a change is made though, you might not get an accurate picture of how often an item gets changed, since multiple changes could be rolled up into a single version of that item.
However, we think what you're doing should be possible with TortoiseSVN.
In the repo-browser, right click on the folder itself (i.e. on the left side of the window), not on an individual file, and select show log on that. There you can browse each revision including the date, which files changed for each revision, and checkin notes if they were supplied.
When you find the revision you’d like to revert to, right click and select export, then provide a new folder. This will save all the project files as they were on that date. You’ll of course need to be careful of the scenario where two packages have interdependent changes, but were checked in separately (and therefore will have different revision numbers), e.g. when moving an item from package A to package B - make sure that you revert to the modified versions of both A and B.
Once you’ve got a specific version exported, you can open that up (from your new folder) in CaseComplete.
Standard caveats apply, of course: TortoiseSVN is a third-party program, so we can't be held responsible for data loss, its support or use, etc.