iBGP as an IGP - Static routes between the peers?

Hey All,

We are beginning to lab/test using iBGP as our only IGP and we're having a split opinion on how to get the routes for the peers themselves around.

We're a fairly typical enterprise, and the largest site has something like 4 routers that will need to be part of the mesh. One part of the design (partly technical, partly political) is that some of the routers must transit L3 through another to get to some of their peers, so I can't just stick everything in the same L2 /24 and have every next hop be connected.

The portion we have a split opinion on, is do we just set "redistribute connected" everywhere, and let the recursive lookups figure it out, or do we set /32 static routes pointing at the (known) L3 next hop for all of the peers. We will never scale past ~5 routers, so the overhead of /32 routes and needing a full mesh isn't a big deal. Nothing as complicated as wanting/needing to set up a Route reflector.

We see pros/cons to both and curious what others might be doing.