<p>Is it possible to use an ocx (ActiveX Control) on a winform (probably adding it programatically) without first having the ocx registered with regsrv32?</p>

<p>What I'm trying to achieve is to enable xcopy installation. I've had the "AxInterop.<em>.dll" and "Interop.</em>.dll" file generated from my dev machine.</p>

<p>I've seen the possibility of calling a COM dll without first registering it (<a href="http://www.codeproject.com/KB/library/ProSysLib2.aspx?fid=1524721&amp;df=90&amp;mpp=25&amp;noise=3&amp;sort=Position&amp;view=Quick&amp;select=2659721&amp;fr=28#xx2659721xx" rel="noreferrer">ProSysLib</a>, according to the author, but I haven't tested it yet), since ocx is also COM based, thus I assume that there must be some way to do that as well.</p>

Yes, this can be done.  You must assume your application will only be deployed on Windows XP (or Windows Server 2003) or later, and then you can use what is called 'registration free COM' to make this happen.
Essentially what you do is create a manifest file for the ActiveX control DLL so the Windows loader & COM DLL's know what its registration is without having to put that in the registry.
A walkthrough of what to do is in this article on MSDN:
Registration-Free Activation of COM Components: A Walkthrough
"Step 6" and "Step 7" in that article contain
everything
you will need.
I just tried this out on one of my own C# programs that uses a Microsoft ActiveX grid control (the old "MS Flex Grid") and it works just fine. Make sure you create a manifest file for both your application and the COM DLL, and substitute the appropriate GUIDs in the right places. You may need to use OLEVIEW to dig out the right IDs to use from the ActiveX DLL if you don't have them handy.