I've flown StratoLoggers (SL100 and SLCF) as well as an EasyMini and an Eggtimer TRS (haven't used the non-TRS version). I like them all, and for basic DD I think any of them will do the job just fine.
In my 4" rocket I fly redundant altimeters, a SLCF and an EM. I found it a bit easier to program the EM via its software, so I left the SLCF as the 'primary' configured for its default apogee and 700' main, and tweaked the EM to a 2s delay on the drogue and 600' on the main. It is nice that you can simply use any USB micro-B cable with the EM, the StratoLogger's data cable isn't particularly inconvenient but it is less-standard. I've had no charge firing issues with any of the SL100/SLCF's I've used or the EM. I used only magnetic switches for activation and they've always turned on/off without any firing issues.
I do like the SLCF's loud speaker and the extra data it gives using it. When you power-up the EM it simply beeps-out the battery voltage and goes straight to continuity beeps. The SLCF (and SL100) beep out their mode (which gives a basic indication of drogue/main settings), the main altitude setting, and the last flight's peak altitude, then battery voltage and continuity beeps. Similarly, at landing the EM gives out some beeps though I haven't figured out if they really mean anything (the manual makes no mention of anything other than the landing phase beep), the SLCF beeps out the max altitude and max velocity, AND periodically makes a pretty loud 'warble' that can help lead you to the rocket which I really like. The SLCF's beeper is much louder than the EM's also. Between the two I like the SLCF better for what it does 'out of the box', while the EM seems a bit more user-friendly to me on the configuration and data download (the app has a bit more fit & finish, on the Mac at least).
I flew the TRS in a rocket where I wanted both deployment and tracking in the nose (the other rockets have dedicated e-bays and Eggfinders in their noses). The tracking part works great and configuring it via the LCD unit or serial is pretty easy, I never really did get what I wanted with the deployment part, though I wasn't doing simple e-matches like the other altimeters. I wanted to use a hot-wire cable-cutter, but had lots of trouble getting the TRS to output enough current to actually get the wire hot. While dialing-in the nichrome resistance I managed to fry the transistors on the board more than once also (fortunately they're easy to replace). I wound up cutting a piece of copper to put under the transistors for extra heat-sinking and dialed the resistors in to get the right current to get the wire temp I wanted, but the activation time just wasn't long enough to reliably burn through even the tiny zip ties I was using. I had no trouble melting the zip ties using my SL100, I just didn't have space in the nose for both a tracker and an altimeter (and batteries for each). That rocket is in need of a rebuild now (an RMS-EZ early motor eject did it in), I'll go to a more conventional DD with a proper e-bay, I may keep the TRS in the nose just for tracking and an additional flight logger, maybe a backup charge for the main. Not sure whether I'll put another SLCF or EM in this rocket's e-bay, I might lean slightly towards the SLCF. The TRS is also really handy for ground testing since you can fire the charges remotely using the LCD unit, so I've moved it from rocket to rocket specifically for ground testing even if that's not the altimeter I normally use in that rocket.
Data-wise, I find the TRS flight log the 'glitchiest', for example it tends to have trouble with both lift-off and motor burn-out on my rockets (the AltimeterTwo has had similar issues with burn-out on the same rockets), I didn't see any ascent issues with the SLCF or EM. At apogee during separation I have seen some fairly wild readings from the SLCF (the altimeters are well-isolated from the actual charges), the EM seems more stable in that regard. The velocity filtering done by the SLCF is a bit odd, it often reports the top speed ~0.5-1 seconds after burn-out, and touchdown gets a bit funky also. The SLCF records at a constant 20Hz the entire flight, the EM is 100Hz up to apogee then 10Hz from then on to save on storage space. The TRS is 20Hz to apogee then 2Hz down for the same reason. The EM adjusts its log timing such that liftoff is at T=0 with some ground data before (the TRS also seems to adjust but has no data before T=0), the SLCF captures some fixed number of samples before its launch-detect but the first sample is called T=0, which generally means lift-off occurs around 0.4-0.6s in my logs (not that adjusting all of the times in the final spreadsheet isn't a fairly easy task). Correlation on max velocity and apogee (once removing any obviously-bogus readings from the more glitchy ones) has been good between all of these altimeters (as well as with altitude on the AltimeterTwo and AltimeterThree and velocity readings on the A2 when it doesn't report totally bogus values).
Support-wise, the Eggtimer Rocketry has been great, Cris is very helpful both on email and in this forum. I've gotten pretty good support from Altus, and I haven't had much luck getting my emails answered by PerfectFlite. While the AltimeterTwo/AltimeterThree are not deployment altimeters I will say that Jolly Logic's support has also been great.
So from my experience so far, I'd probably rate the SLCF just a tiny bit above the EM, and the TRS not far behind (and also having tracking in the TRS is a huge plus for space-constrained rockets). None of these have accelerometers which I miss, I tend to fly an AltimeterTwo and/or AltimeterThree in these rockets to get accelerometer data as well. I'm thinking about moving up towards an altimeter that can do airstarts, and I'm really tempted to go with either the EasyMega or the TeleMega (if I decide to go for a HAM license as well, getting the real-time feed into the Altus software looks like it could be pretty sweet).