ADO Performance vs OO4O Performance

Question

I have managed to get OO4O to outperform ADO in returning a resultset. I have not managed to get OO4O to outperform ADO in executing a PLSQL Procedure. I will place my vb code below. Right now my ADO code is performing 8 times faster than my OO4O code.
Chris
Dim dsess As OraSession
Dim dbase As OraDatabase
Dim dParams As OraParameters
Dim p_return As String
'Create the OraSession Object.
Set dsess = CreateObject("OracleInProcServer.XOraSession")
'Create the OraDatabase Object by opening a connection to Oracle.
Set dbase = dsess.OpenDatabase(tnsString, loginString, 4)
Set dParams = dbase.Parameters
dParams.Add "P_RETURN_TX", P_RETURN_TX, ORAPARM_OUTPUT, 1
dParams.Add "P_START_NO", 1, ORAPARM_INPUT, 2
dParams.Add "P_COUNT_NO", 10, ORAPARM_INPUT, 2
dParams.Add "P_USER_LOGON_TX", USER_LOGON, ORAPARM_INPUT, 1
dParams("P_RETURN_TX").MinimumSize = 10000
dbase.ExecuteSQL ("Begin TOPS_PCK.LIST(:P_RETURN_TX, :P_START_NO, :P_COUNT_NO, :P_USER_LOGON_TX); end;")
p_return = dParams("P_RETURN_TX").Value
dParams.Remove "P_RETURN_TX"
dParams.Remove "P_START_NO"
dParams.Remove "P_COUNT_NO"
dParams.Remove "P_USER_LOGON_TX"
dbase.Close
Set dbase = Nothing
Set dsess = Nothing
getSP = p_return

Answer 1

Does the ratio hold true if you include only the procedure call and eliminate the COM invocation and intialization code (in other words remove the database and session initialization code)?
I imagine the overhead to initialize OO4O might be more.