Maybe as a workaround, the const string could be declared as an array of char instead of as a string. That way it would no longer be managed.
That way there cannot be a memory leak since the array will be in the data segment. That said, it is possible to put the array on the heap or in a virtual block but then ensuring the block is freed upon program termination takes a little more work.
I just figured I'd mention those possibilities.
HTH.
@BrunoK,
An academic point, it would be better to typecast the pointer resulting from @such to ptruint than qword.