AFAIK there is no way to do this through the TestComplete libraries (which really are not libraries, but just a couple of members from the main application that are exposed Public...)
What we do here is feed everything to a SQL database. It serves as a central hub for all the tools we created to manage the test environment. In our case we just feed the final log path to a table entry, but you could also write an entry in there for each subitem. One of our rows looks like this:
ID Duration LogDate Success ResultsPath ExBuildID RunningNow TestCode EditionCode LangCode DbmsCode MachineName TestShortName ProductName
160 2.2 2012-11-29 14:50:19.197 1 \\LOGSVR\LOGS\MYPRODUCT\11.5.15.729\VMTESTSRV15\Results 2012-11-29\DBD-001 ERP ACCESS 1 8542 0 DBD-001 ERP EN Access VMTESTSRV15 Dashboard test MYPRODUCT
Once everything is fed in there, you can run different queries on the table to get some metrics. For example, we also cross reference the contents of the log table to our development tickets system to match tests to known issues waiting to be corrected, etc...
