This can be useful in naming objects and in custom logging. Right now the user has to find some way to record it separately, but TestComplete already knows this name so it should be easy to expose. ...
I would also suggest to get some 'call stack'; at least the direct caller of the current routine, and if possible N (or all) the call stack levels available.