A simple example on my pretty virgin P4V install. (Edit: this is the free 20 seats one, unlimited size and no time expiration or anything like that)
Note that when collaborating if people make changes on a file you are working on as well it does allow you to resolve changes, but if they are binary you might want to exclusive check them out so no one can alter them and they have to wait until you are done so then can start adding their changes after your's are in the depot.
But usually everything I do is text based so.
This is the PSoC KitProg project that I modified just a couple of i/o pins and change the version number so it's compatible with current cypress tools.
First I did check in the full project as I downloaded it and intended for Creator V2.0.
Then I proceeded to clean temp files that really don't belong on source control.
Then I fired up Creator 3.0 and allowed the program to upgrade my modules, I added notes on modules I didn't let the software upgrade.
Then I changed the programming pins.
And last I upgraded the version of KitProg because current cypress tools expect 2.08 and will refuse to use my custom 2.03 even if they are compatible.
You can open a changelist and it will show you what files changed.
And you can diff them as well
Many other things too. And even if I use this locally, the depot can be in the cloud. Hopefully your datacenter will make backups or you will have to do that, just incremental backups will work and doing full ones every now and then.
If many branches and users, you can do revision graphs to see how a piece of code changed all the way to it's original inception.
Edit 2:
Also Perforce has an API so you can do your own extensions if you are so inclined to.
http://www.perforce.com/product/components/apis20 seat download page:
http://www.perforce.com/downloads/Perforce/20-UserSupports Unix, Windows, Linux, and Macs.
And it's Git compatible to some degree, haven't used that yet but pretty much it can show your depot as a Git, or is it the other way around? not sure but you can read the details here:
http://www.perforce.com/git-fusionAlso it has peer review capabilities via their Perforce Swarm.