[Perforce Integration] Duplicate asset, renamed to match deleted parent, results in undesired marked deletion of duplicate asset in Perforce

(Pulled from associated UDN, slightly reformatted)

Hello,
I have a long lasting bug which can cause unwanted asset deletion on perforce when manipulating assets.

Have a folder in content with 1 versioned assets (A) and an active perforce connection

1. Duplicate asset A, name it B -> you now have B "Mark for Add" in perforce
2. Delete Asset A -> A is now marked for delete in perforce, B Still "Mark for add"
3. Rename B into A -> B is no more on perforce, A is still marked for delete

Expected Result: A should just be "Check out" and not marked for delete.