Class-level behavior wrapping works with a List<Func<ClassBehavior>> instead of a List<Type>, opening the door for convention authors to supply behaviors in ways other than simply providing the behavior type name.
Fixture-level behavior wrapping works with a List<Func<FixtureBehavior>> instead of a List<Type>, opening the door for convention authors to supply behaviors in ways other than simply providing the behavior type name.
Case-level behavior wrapping works with a List<Func<CaseBehavior>> instead of a List<Type>, opening the door for convention authors to supply behaviors in ways other than simply providing the behavior type name.
To give convention authors more control over the construction of their custom behaviors, convention authors can supply already-constructed custom behavior instances when wrapping Class/Fixture/Case behavior, instead of being limited to supplying a custom behavior type name.
Merge pull request #73 from plioi/ExtendBehaviorWrappingApi

Allow convention authors to construct their own behavior instances.