onetimesetup: system.nullreferenceexception : object reference not set to an instance of an object.
Start NUnit, but don't run the tests. In visual studio make sure you have the project that contains your nunit tests open. Then in visual studio press ctrl+alt+p. This will bring up the list of processes to attach to. Choose the nunit-agent.exe process. If there is more than one nunit-agent.exe process you can ctrl+ to choose all of them. You may have to check the Show processes in all sessions and/or Show processes from all users to get the nunit-agent.exe to show up. At this point you should be able to debug your test.
Now you can set a breakpoint at the constructor call to CardTable. As you step through the debugger you should be able to identify your null object reference error.
An alternative to stepping through the code is to choose in the menu Debug->Exceptions... in the dialog that shows check the thrown box next to Common Language Runtime Exceptions. This will cause the debugger to stop on any execptions handled or unhandled when they are thrown. This removes the need for the breakpoint, but if you have exceptions being thrown that are caught, it may be more hassle than the breakpoint method above.