It is common agreement that software engineering can meet its challenges only if disciplined reuse and composition mechanisms can be established in both theory and practice. In this paper we provide a thorough analysis of the percolation pattern and three alternatives to it. As result of this analysis we get that each of these alternative checking strategies ensures behavioral subtyping and therefore good reuse properties. However, none of them allows for modular reasoning due to missing success or failure conformance over class hierarchies