Some implementations of alternative concordion runners inherit directly from `BlockJUnit4ClassRunner` (eg. the [ConcordionPlus](https://code.google.com/p/concordion-plus/source/browse/trunk/src/main/java/org/agileinsider/concordion/junit/ConcordionPlus.java) runner.

It would be great if we could allow these runners to use this new enhanced reporting mechanism too. A couple of potential options would be to:

* create a new class-level annotation (eg. `@ConcordionRunner`) and invoke `runConcordionJUnit4Test()` if the `s.value()` class has this annotation. This has the downside that existing Concordion runners would need to be changed to add this annotation.
* always try calling `runConcordionJUnit4Test()`. If it fails since the fixture doesn't exist, fall back to running as a JUnit test. The downside of this is that it would impact execution time if users are running JUnit tests from Concordion (I've never come across this though).