Renaming a user back to a prior used DN results in incorrect order in Notes ID-Vault

There are several use cases, which lead to a problem, where the expected order of DNs in the a users's Notes ID-Vault document gets messed up leading to not showing the most recent DN in first place (column IDOwner).

If for example a user gets renamed by accident and an administrator renames the user back to the exactly prior name.
eg User Right/wyd => User Wrong/wyd => User Right/wyd

This is even more likely to happen in larger environments, where eg a department is part of the naming/certfication scheme and reorganisations are done leading to a user switching back to a prior department.
eg User Test/Department X/ACME => User Test/Department Y/ACME => User Test/Department X/ACME.

Although the rename process back to a prior name is processed correctly and also the Notes-ID gets updated properly and update in the Notes ID-Vault, the most recent DN is not in first place in the user's Note ID-Vault document.

Expected behaviour:
The order of DNs in a user's Notes-ID Vault document should correctly reflect all renamings even back to a DN used prior.

Screenshot of the Notes ID-Vault showing the incorrect order of DNs after the second rename back to the prior name.