Here is the list of ODIs Australia lost while Bevan was playing, sorted by runs scored in the opposition's innings.
Team records | One-Day Internationals | Cricinfo Statsguru | ESPNcricinfo.com
The main criticism of Bevan as an ODI batsman was that he didn't score fast enough. I wanted to test this hypothesis by looking over the games lost by Australia while Bevan was playing. Particularly those where the opposition set large totals, or chased down the total set by Australia.
It makes sense then that we need to take into account a) the size of the total the opposition set/chased; and b) Bevan's innings in that loss.
Low total innings are obviously not important for this, since strike rate doesn't matter very much at all if you are chasing 250 or less (average strike rate 83).
Full Scorecard of Australia vs Sri Lanka, Australian Tri Series (CB Series), 6th Match - Score Report | ESPNcricinfo.com
Pretty large defeat. Bevan struck at 80 in a chase, scoring 41. Martyn batted 4 and scored 40 at a lower strike rate. Hayden scored 35. No other batsman contributed. Conclusion: Bevan was one of the top two Australian batsmen during that innings. Loss was due more to other batsmen failing than Bevan's strike rate.
Full Scorecard of India vs Australia 1st ODI 2001 - Score Report | ESPNcricinfo.com
60 run defeat. Bevan scored 49@87. Second top scoring batsman for Australia. Conclusion: Bevan's strike rate non issue.
Full Scorecard of South Africa vs Australia 7th ODI 1997 - Score Report | ESPNcricinfo.com
109 run defeat. Bevan 29@107. Second top scorer. Conclusion: Bevan's strike rate inconsequential. Possibly even too high for the match situation.
Full Scorecard of India vs Australia, Pepsi Triangular Series, 1st Match - Score Report | ESPNcricinfo.com
41 run loss. Bevan top score with 65@79. Dismissed with 80 runs off 9 overs to go. Conclusion: could be argued (very weakly) his strike rate wasn't high enough. Loss was more due to other batsmen.
Full Scorecard of Australia vs India, ICC Champions Trophy (ICC KnockOut), 3rd QF - Score Report | ESPNcricinfo.com
44 run loss. Bevan 8@57. Woeful innings. Part of the cause of the loss. The chase wasn't close enough to make the 14 balls he chewed up to be anywhere near the difference between victory and defeat.
Full Scorecard of Australia vs India, Australian Tri Series (CB Series), 5th Match - Score Report | ESPNcricinfo.com
19 run loss. Bevan 41*@95. A rare chase where Bevan ended not out and Australia lost. His failure here was placing too much faith in the tail. All 4 bowlers striking at less than 70. Conclusion: strike rate not an issue but a failed chase.
Full Scorecard of India vs Australia 3rd ODI 2001 - Score Report | ESPNcricinfo.com
118 run defeat. Woeful innings. Match best forgotten entirely. Aus all out in 36 overs. Conclusion: strike rate not an issue.
Full Scorecard of Australia vs Pakistan, NatWest Series/Challenge, 8th Match - Score Report | ESPNcricinfo.com
36 run defeat. Woeful innings. The 9 balls he lasted didn't make a difference to the loss. Arguably if he'd had an innings of note Australia could have won the match. Conclusion: strike rate not an issue.
Full Scorecard of West Indies vs Australia 5th ODI 2003 - Score Report | ESPNcricinfo.com
39 run loss. Bevan 31@77. Arrived needing 140 runs in 18 overs. Lost the last recognised batsman needing 109 off 13 overs. Conclusion: left with too much to do. Strike rate not an issue.
I'm going to stop there. These were the top 9 batting performances by Australia's opposition during Bevan's playing time which resulted in an Australian loss. It can maybe be argued that his strike rate was an issue in one of those cases if you're being extremely hard on him. In every other loss Bevan's strike rate was a non issue. In many of them he had one of the highest strike rates in the side and was one of the leading run scorers.