EDIT: bobandbill beat me to the review by being in Australia, so some things I say may be redundant.
About the beta thing - PC has its own little Beta Corner you can check out if you need a beta, and you don't even need to go through the hassle of document transfers and what not. All you would need to do is send your beta the manuscript via a PM or e-mail or however you're communicating. FF.net isn't the only place with betas, and forums are usually pretty good with this sort of stuff.
Anyway, onto the story.
I found the game-mechanics incorporated into the story disjointing and weird, because in reality, I wouldn't go around and say, "I have more levels than you do," or, "I need to get more HP by eating some pizza." I mean, think about it. You go on about how Pokemon have 'HP' and 'levels' so I get that you're trying to follow the games, but is that really the way to go about telling a Pokemon story? Just think about it. I personally find it weird if a character says to another that they have a higher Attack stat, which could easily be translated to a character claiming they're physically stronger. I'd suggest mixing in the game mechanics into reality, just as I mentioned with the Attack stat. Generally speaking, Pokemon Centers refresh Pokemon or literally heal them after battle, so referring to constitution as HP, to me, sounds funny, and not in the 'ha-ha' way.
The story starts out in en media res, which is generally a solid opening if you want to get readers involved. After all, watching people fight is far more entertaining than watching people talk about their new iPhones. However, I found the battle itself weak. There are a number of odd things running around I'll get to later, but most prominently, you don't really describe things particularly well, which is practically a given when you use the first-person narrative. The battle scene read as command-attack-attack-command-attack-attack, etc. It was a bit predictable and bland. There wasn't much flavor to the course, a pizza without any cheese or tomato sauce. There are, however, many sentences that are simply straight attacks and lines of dialogue with the trainers shouting commands. However, what you should have focused on was Benki's view on the battle itself. Benki, obviously, was very excited in the battle, since you explicitly stated that, but his thoughts are conspicuously absent after you go on about 'adrenaline' and whatnot. Keep in mind that there are more to battles than just Pokemon hitting each other as hard as they can; think about why Pokemon battle and how they feel in that moment. It's a tense atmosphere, no matter how light the actual battle is, and it's brutal in many ways. A Pokemon's few, subsequently, would reflect a lot of chaos on confusion, since they're stuck right in the middle of a battle. Emotions run high. But all you've said was Benki was excited.
And the keyword was said. If you haven't heard of "show, don't tell" you just did. What it means is what the name implies: Show readers what's happening rather than telling them. Now, that can be tricky, but take this for example:
Also, can Benki feel the flames on his back? I'm just curious.
I'm not too sure what to make of this story. There's a lot of things going on at once, most notably with Benki's odd dream, and the story itself starts out in a weird place, which I find delightful. However, I felt that some bits of the story felt clunky when they transitioned, happening in bits and pieces rather than flowing together as a whole. But maybe you did this on purpose - I'm not sure. In any case, I highly suggest that you read your story out loud before you post it so that you can proofread. Reading aloud will help you notice some things you wouldn't read mentally. There's something about hearing what you wrote that gets you to click in some instances. This should help out with any clunky prose or anything that just sounds awkward; if something's hard to read, chances are you can do something to make it easier and less of a strain to interpret.