Current test coverage is too low for a such complex system.
It's worth to cover as much branches as possible

Now resolution cycle detection is turned on always.
This logic is mixed with normal ioc resolution.
It's worth to separate these responsibilities.

This should be done something like:

var builder = new IoCBuilder();

builder.Register<T1>();
...
builder.Register<Tn>();

builder.Finish();

var ioc = new CycleDetection(builder.Result);

ioc.Resolve<SomeType>();

Or like:

var builder = new CycleDetectionBuilder(new IoCBuilder());

builder.Register<T1>();
...
builder.Register<Tn>();

builder.Finish();

var ioc = builder.Result;

ioc.Resolve<SomeType>();

Now if some type A has 2 constructors the most long one is selected as a candidate for resolution.
If it fails (some of parameters can't be resolved) then next one is used and so on.

This leads to unpredictable changes in behavior when missing parameters are registered.
We should use RegisterType if it has only 1 public constructor.

It also can gain speed of RegisterType as most of code can bemoved to Register time

It can be usefull to check if some factory was used during resolution step.
This can help you to check if some factories are redundant or wrong one was used.
This feature can be implemented in the same way as cycle detection