Slurs are not played back properly, depending on how they are entered

I am still using 0.9.5, just for the record, so I don't know if 0.9.6 has fixed this or not (I'm concerned with the bugs I see being reported on 0.9.6 that it might be best for me to wait a bit before updating again, since I'm kind of in the middle of a deadline for an arrangement I'm working on). If someone else would like to take the examples I've attached and enter them in and see how they are played back by MuseScore in 0.9.6, I'd be interested to know if the problem still exists. It's not an important issue just at the moment for me, but it does help in ensuring proper rhythmic accuracy. I'm concerned that it would be a waste of time to export the file to .wav as it would still play notes that should not be articulated (which would be detrimental for both practice and publication purposes down the road).

Expected behavior: When a note value is entered and then later tied (or slurred) to another note of the same pitch, the playback option should not articulate the second note.

Actual behavior: Depending on how the note value is entered in, slurs may or may not be played with an articulation between the two notes that should be slurred together (see "Improperly Played Slurs" attachment for an example of a rhythm that MuseScore does not play back correctly).

Exceptions to this behavior: If a note value is entered so that Musescore automatically ties the note across a bar line, the notes are played as written with no articulation during the resulting tie/slur (for example, in 3/4, entering a dotted whole note creates two dotted half-notes which are tied across the bar line. These notes are played back as one 6 beat long note. See "Properly Played Slurs" attachment for example of this).

For the record: this is my first real bug that I've found yet at this point, and during a recent vacation, I used the program for like 16 hours in 2-3 days (and, courtesy of the piece I was working on, found this bug right away) and probably put in 2/3 of the work needed on the arrangement I'm working on. I wouldn't consider myself an expert Finale user, but- courtesy of my education- I am VERY well versed in the program. Frankly, I am incredibly impressed with how far MuseScore has come along in the short time that it's been in development. It probably took Finale 10 years to get to this point. If MuseScore development continues at its current pace, in 2-3 years, you guys can make it so that Finale will have to blow its users out of the water with quality changes in order to compete with open source freeware like this (and then it will actually be worth the $250 that they make students pay). At current pace, you'll be about evenly matched and just as user friendly as Finale in 3-5 years. Thank you for all your hard work and dedication to something that you know you won't be paid for!!!