Node revision clash on node edit or new node save - not related to node deletion

Okay I've installed the updates and have been still having problems with id's clashing and discovered the following: When this module is enabled, I get an error on new node creation like this:
user warning: Duplicate entry '767' for key 'PRIMARY' query: INSERT INTO uuid_node_revisions (vid, uuid, nid) VALUES (767, 'f4d2be04-d555-11df-be90-002219221c49', 753) in /home/autop5/public_html/webmanager/sites/all/modules/uuid/uuid.module on line 62.

What I've discovered is that when a new node is created, node id of 753 is created but version id of 767 is created for that node. The strange thing is that I made sure when testing this that there wasn't already a 767 vid taken. I made sure all the uuid entries, term data, location instances (since i'm using location module) were empty and did a sql query on both the node and node revisions table to make sure that all nid's and vid's match. Still, for some reason a new node is not getting the next available vid if its available. So deleting 767 vid does not make 767 available again as a new vid. Maybe this is a core bug but the UUID module has a problem with it and reports an error because of it. Maybe others aren't seeing this problem because all of their nids and vids have always matched but because I had revisioning enabled on a content type at one time, I had alot of mismatches. I don't have revisioning enabled on any content types now by the way. Is it possible that UUID code overcomes this issue somehow perhaps in the same way the location module has with location ids?

Is anyone else at all experiencing this problem and have a solution?

I've installed the latest dev version which I assume contains those patches? and... same error occurs. From a theory standpoint, from what I've read no 2 tables should share the same primary key name. Isn't the structure of the UUID tables essentially using the same primary key name from the node and the node_revisions tables that could be causing the errors for me? Shouldn't the UUID table have its own unique primary key with nid and vid as foreign keys? This is the only reason I can think my error is occurring...

Let me rephrase my statement, no 2 tables should "HAVE" the same primary key name, didn't mean to say "share". Anyhow, am I seriously the only one still getting this error? I just can't believe I've tested this on multiple installs and keep getting this error but noone else seems to be experiencing it.

Got this error when applying version 3 patch

Parse error: syntax error, unexpected T_CASE in /home/~/public_html/~/sites/all/modules/uuid/uuid.module on line 77

Tried to apply version 2 patch and it fails. I give up... i'll just wait for the next functional release.

Thanks anyway.