First of all, I think you're probably in a position that many of us have been in. Moving into a role as a BA is a very natural progression for many testers. I mean there are definite similarities in the positions and I think they have many of the same requirements (not job requirements but personality requirements).
I don't know if you'll see this become a position itself. I think most larger organizations try to discourage splitting time of their employees between two separate positions. However, in smaller organizations, maybe even some mid-level organizations, this can happen. It probably comes from the fact that we're working with the application all day, part of our job is understanding or anticipating how a product will be used, understanding what's user friendly and what isn't. Essentially we have all the skills you'd want in a BA.
I do disagree that there is a conflict, though. Or, rather, there is a conflict that's different than what you think it is. Why can't we test our own work? As a BA you shouldn't be providing biased information. You can't go in as a BA and make suggestions based on how you would use the application. The data you collect has to be accurate of a target market. So you should be finding, even as a BA, that there are aspects of your research into an industry, customer, or applicaiton, that you don't agree with. However, it doesn't really matter what you think if it's shown to be how that consumer is using it. Now, let me clarify, when I say USING I don't 'mean making do with'. I mean if a product functions how a consumer expects or wants it to function then it's correct, regardless what you 'think' it should be doing.
So, no, I don't think that there is a conflict between tester and BA. I think that as a BA you should actually be even more attuned to what the product should and shouldn't do. This information is extremely valudable to producing the right product.